Multiple-slice application delivery based on network slice associations

ABSTRACT

A device can receive, from first user equipment, information that relates to a first application, where the information includes a plurality of S-NSSAI. The device can determine whether the plurality of S-NSSAI are configured as a group of associated S-NSSAI. The device can determine that a preference is to be given to one of: communication sessions associated with the first application relative to a communication session associated with a second application, that does not utilize multiple network slices, of the first user equipment or second user equipment; traffic flows associated with the first application relative to a traffic flow associated with the second application; or a plurality of network slices associated with the first application relative to a network slice associated with the second application. The device can perform one or more actions based on determining the preference to thereby facilitate a particular functionality of the first application.

RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.16/351,853, filed Mar. 13, 2019 (now U.S. Pat. No. 10,667,179), which isincorporated herein by reference.

BACKGROUND

5G/New Radio (5G/NR) is a next generation global wireless standard.5G/NR provides various enhancements to wireless communications, such asflexible bandwidth allocation, improved spectral efficiency,ultra-reliable low-latency communications (URLLC), beamforming,high-frequency communication (e.g., millimeter wave (mmWave)), and/orthe like.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1A and 1B are diagrams of one or more example implementationsdescribed herein.

FIG. 2 is a diagram of an example implementation described herein.

FIG. 3 is a diagram of an example environment in which systems and/ormethods described herein can be implemented.

FIG. 4 is a diagram of an example functional architecture of an examplecore network described herein.

FIG. 5 is a diagram of example components of one or more devices ofFIGS. 3 and 4.

FIG. 6 is a flow chart of an example process for multiple-sliceapplication delivery based on network slice associations.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description of example implementations refers tothe accompanying drawings. The same reference numbers in differentdrawings can identify the same or similar elements.

In a wireless telecommunications system (which can be referred to hereinas “the system”), such as a 5G wireless telecommunications network,network slicing allows for multiple virtual networks to run on a singlephysical network to support multiple services, applications, and/orentities (e.g., end users, customers, such as organizations that providea service to end users of the wireless telecommunications system, and/orthe like). In some instances, when a user equipment (UE) requests aconnection (e.g., protocol data unit (PDU) connectivity) to the networkfor an application and/or service, the UE provides the network withinformation associated with the UE, the application, and/or the service.Such information can include network slice selection assistanceinformation (NSSAI), which can include a collection or list ofindividual, single-network slice selection assistance information(S-NSSAI) (referred to herein individually and collectively as“S-NSSAI”) that identify respective network slices associated with theUE. In such cases, a network slice selection function (NSSF) of thesystem can determine a network slice instance (NSI) (e.g., a virtualnetwork of network functions (NFs) and other resources to support one ormore S-NSSAI) for the S-NSSAI. The NSSF can provide, to an access andmobility management function (AMF), an NSI identifier (NSI ID)associated with the NSI. Further, the AMF can identify a sessionmanagement function (SMF) to provision a communication session of anetwork slice, using the corresponding NSI, for the UE. The UE can beserved by multiple NSIs (e.g., a first communication session of the UEcan be served by a first NSI and a second communication session of theUE can be served by a second NSI).

Resources can be assigned to a communication session of a network slicebased on a priority associated with the communication session. Whenthere are insufficient resources in the network to support thecommunication session of the network slice, the network can preemptresources of an existing communication session with a lower priority inorder to admit the communication session of the network slice.Similarly, traffic flows of the communication session of the networkslice can be scheduled before a traffic flow of a lower prioritycommunication session.

Sometimes, an application of a UE can utilize multiple network slices.In such cases, respective communication sessions (e.g., PDU sessions)can be provisioned on the multiple network slices in order to provide aparticular functionality of the application. However, informationelements of the S-NSSAI are not defined to enable the network todetermine an association of multiple network slices and an application.Accordingly, previous techniques to determine admission and/orpreemption of communication sessions, scheduling of traffic flows,and/or allocation of resources lack awareness of associations betweennetwork slices and applications. Accordingly, previous techniques canresult in an impairment of an application when admission and/orpreemption, scheduling, and/or resource allocation is performed withoutregard to whether a communication session of a network slice is one of aplurality of communication sessions that are associated with anapplication. Moreover, previous techniques can result in a disruption tosome communication sessions associated with an application withoutdisrupting other communication sessions associated with the application.Consequentially, the communication sessions that are not disrupted cancontinue to consume and waste network resources despite an impairment tothe application.

Some implementations described herein enable a radio access network(RAN) of a telecommunications system (e.g., a 5G wirelesstelecommunications network) to determine an association among aplurality of S-NSSAI (e.g., a plurality of S-NSSAI identifying aplurality of network slices utilized by an application). Furthermore,some implementations described herein enable the RAN to determine, basedon the association of the plurality of S-NSSAI, that a preference is tobe given to an application associated with the plurality of S-NSSAI(e.g., a preference for communication sessions associated with theapplication, a preference for traffic flows associated with theapplication, etc.) and/or that a preference is to be given to aplurality of network slices identified by the plurality of S-NSSAI(e.g., a preference to allocate resources to the plurality of networkslices).

In this way, the RAN can perform communication session admission and/orpreemption, traffic flow scheduling, and/or resource allocation withregard to groups of associated network slices. For example, the RAN canperform communication session admission and/or preemption, traffic flowscheduling, and/or resource allocation so as to avoid disruption to acommunication session of a network slice that is one of a plurality ofcommunication sessions that are associated with an application.Accordingly, impairment to applications that utilize multiple networkslices can be reduced and network resources, otherwise wasted when acommunication session continues to serve an application that isimpaired, can be conserved.

FIGS. 1A and 1B are diagrams of one or more example implementations 100described herein. Example implementation(s) 100 illustrates variousportions of a wireless telecommunications system (referred to herein asa “wireless network”), which in some implementations can be a 5Gwireless telecommunications system. Example implementation(s) 100 can bea 5G wireless telecommunications system, a 4G wirelesstelecommunications system, a long-term evolution (LTE) wirelesstelecommunications system, an LTE-Advanced (LTE-A) wirelesstelecommunications system, and/or the like.

As shown in FIGS. 1A and 1B, example implementation(s) 100 can include aUE wirelessly connected to a RAN at a base station. The base station canbe connected to a data network via a core network. The UE can run anapplication that involves communicating with the data network, andtherefore the UE can enter into a communication session (e.g., a PDUsession) with the data network via the RAN and core network. The UE andthe core network can communicate application-specific data during thecommunication session. In some implementations, to permit the UE toenter into the communication session with the data network, the UE cansend an initial request to register with the core network.

The UE can be a communication and/or computing device, such as a mobilephone, a smartphone, a laptop computer, a tablet computer, an Internetof Things device, and/or the like. The base station of exampleimplementation(s) 100 can include an access point of a RAN, such as a 5Gnext generation NodeB (gNodeB or gNB), an LTE evolved NodeB (eNodeB oreNB), and/or the like. In some implementations, the base stationfacilitates a communication session by communicatingapplication-specific data between the UE and the core network. In someimplementations, the base station can have a disaggregated or “split”architecture, including one or more distributed units (DUs) and one ormore central units (CUs), where the one or more CUs can be further splitinto a control plane (CU-CP) node and a user plane (CU-UP) node.

In some implementations, each DU can correspond to a logical node thathosts Radio Link Control (RLC), Medium Access Control (MAC), andPhysical (PHY) layers of the base station. Operations of the DU can becontrolled, at least in part, by the one or more CUs. In general, one DUcan support one or multiple cells, although any one cell is typicallysupported by only one DU. Each CU can correspond to a logical node thathosts Radio Resource Control (RRC) and Packet Data Convergence Protocol(PDCP) functions associated with the base station. Furthermore, in someimplementations, one or more CUs can optionally further host ServiceData Adaptation Protocol (SDAP) functions associated with the basestation. When a CU is split into a CU-CP node and a CU-UP node, theCU-CP node can correspond to a logical node that hosts the RRC andcontrol plane part of the PDCP protocol, while the CU-UP node cancorrespond to a logical node that hosts the user plane part of the PDCPprotocol. Furthermore, in some implementations, the CU-UP can optionallyfurther host the SDAP protocol associated with the base station. In someimplementations, there can be multiple CU-UP nodes in the RAN and eachCU-UP node can be associated with one or more network slices that areidentified via one or more S-NSSAI (e.g., there can be multiple networkslices connecting to a given CU-UP node, a different CU-UP node for eachnetwork slice, and/or the like). Furthermore, a split of layers and/orprotocols among the CU unit and the DU(s) can be flexible and vary fromone implementation to another.

In this way, by disaggregating the base station into one or more DUs andone or more CUs, the base station can be implemented with a flexiblehardware design that allows scalable cost-effective solutions andcoordination of load management, real-time performance optimization,virtualized deployment, and adaptation to various use cases, such asvariable transport latency.

In some implementations, when the base station is split into separateDU, CU-CP, and CU-UP nodes, the various nodes associated with the basestation can be deployed in various ways. For example, in general, therecan be one or multiple DUs, one or multiple CU-CP nodes, and one ormultiple CU-UP nodes. Depending on the particular RAN implementation,one DU can be connected to one or more CU-CP nodes via an F1-Cinterface, one DU can be connected to multiple CU-UP nodes via an F1-Uinterface under the control of a single CU-CP node, one CU-UP node canbe connected to multiple DUs via the F1-U interface under the control ofa single CU-CP node, and one CU-UP node can be connected to one or moreCU-CP nodes via an E1 interface. Furthermore, in some implementations,the CU-CP node and/or the CU-UP node can be deployed in a centralizedmanner and/or a distributed manner in various use cases. For example,the CU-CP node and the CU-UP node can both be centralized, with thecentralized CU-CP node used to coordinate the operation of several DUsand the centralized CU-UP node used to provide a central terminationpoint for user plane traffic. In another example, the CU-CP node can bedeployed in a distributed manner and co-located with a single DU, inwhich case the co-located CU-CP node can supervise the operation of thesingle DU. In still another example, the CU-UP node can be distributedand co-located with a single DU. Of course, in a given RAN, differentdeployment scenarios could be used in combination.

In this way, splitting the CU into separate CU-CP and CU-UP nodes and/orallowing various centralized and/or distributed deployments for the CU,CU-CP node, and CU-UP node can enable flexibility to operate and managecomplex networks that support different network topologies, resources,and new service requirements, enable a functional decomposition of radioaccess between user plane and control plane entities based on apartially decoupled architecture, enable independent scaling andrealization for control plane and user plane functions, and enable thelocation of different RAN functions to be optimized based on thescenario and desired performance. For example, the CU-CP node could beplaced in a location close to the DU to provide short latency forcritical control plane procedures, the CU-UP node could be centralizedin a regional or national data center to favor cloud implementation(s),an additional CU-UP node could also be co-located and/or placed closerto the DU to provide a local termination point for low-latency traffic,etc. Furthermore, the split architecture can support radio resourceisolation and improve resource utilization and provide networkslice-level isolation for an NSI, which can cover a geographic area ofseveral base stations.

In some implementations, each DU can store information relating to oneor more contexts associated with a UE (e.g., a Data Radio Bearer (DRB)ID, S-NSSAI, quality of service (QoS) flow-level parameters, and/or thelike associated with each UE context). Each DU can further store certainnetwork-level information, which can include supported bands, supportedbandwidth, whether the network has a standalone configuration using onlyone radio access technology (RAT) or a non-standalone configurationcombining multiple RATs, whether certain shared spectrum (e.g., sub-6GHz) is shared in a dynamic and/or static manner, and/or the like. Insome implementations, the CU-CP node can store a list of network sliceIDs (e.g., a list of S-NSSAI) and a network slice-to-AMF (e.g.,NSSAI-to-AMF) mapping because there can be an AMF for the entire networkor an AMF for a single network slice. Additionally, the CU-CP node canstore a mapping between network slice IDs and associated CU-UP node andDU combinations (e.g., indicating a DU and CU-UP node configured tohandle traffic associated with a given network slice ID).

The core network of example implementation(s) 100 can include varioustypes of telecommunications core networks, such as a 5G next generationcore network (NG Core), an LTE evolved packet core (EPC), and/or thelike. The AMF of the core network can provide authentication and/orauthorization of the UE. In some implementations, an authenticationserver function (AUSF) component assists the AMF in authenticatingand/or authorizing the UE. Additionally, or alternatively, the AMF cancoordinate with a unified data management (UDM) component to obtainsubscribed NSSAI associated with the UE. The subscribed NSSAI caninclude a list of S-NSSAI that the UE is subscribed to utilize (e.g.,for a communication session). In some implementations, the UE canprovide a particular number of S-NSSAI (e.g., eight S-NSSAI or more,fifteen S-NSSAI or more, and/or the like), within the NSSAI, whensending a UE configuration request. Therefore, the UE can provide theNSSAI to the AMF so that the UE can be associated with (e.g., registeredto, assigned to, and/or the like) an NSI, which can be considered avirtual network that is implemented through various physical resourcesof the RAN and/or NFs of the core network. As described herein, the NSSFcan provide an NSI for an S-NSSAI included in the NSSAI from the UE. Forexample, the NSSF can maintain a mapping of S-NSSAI to NSIs.Accordingly, the NSSF can indicate an NSI selection and/or mapping ofS-NSSAI to NSIs to the AMF to permit the UE to utilize a correspondingNSI (and/or resources of the NSI) for a communication session.

In some implementations, the NSSF can determine a set of network slicepolicies to be considered when selecting an NSI. The set of networkslice policies can set rules and/or requirements at a network level(e.g., for all or a subset of UEs, for all or specific applications, forall or specific geographic areas, and/or the like) and/or a user level(e.g., per UE, per application, and/or the like). The set of networkslice policies, which can be maintained by a policy control function(PCF) component of the core network, can include an area capacity policy(e.g., a data rate capacity over an area), a mobility policy (e.g.,location and speeds of UEs), a density policy (e.g., a number ofcommunications sessions over an area), a guaranteed minimum data ratepolicy (e.g., minimum download and upload speeds), a maximum bitratepolicy (e.g., maximum download and upload bitrates), a relative prioritypolicy (e.g., relative importance of the application and/or UE comparedto other applications and/or UEs), an absolute priority policy (e.g.,objective importance of the application and/or UE compared to otherapplications and/or UEs), a latency rate policy (e.g., an end-to-endcommunications transmission time), a reliability policy (e.g., acommunications transmission success rate), a resource scaling policy(e.g., an ability or range for scaling resources up or down), and/or thelike. In some implementations, the set of network slice policies candefine a low latency performance requirement (e.g., an end-to-endcommunications transmission time less than or equal to a threshold, suchas 10 ms), a high latency performance requirement (e.g., an end-to-endcommunications transmission time greater than a threshold, such as 10ms), a low reliability performance requirement (e.g., a communicationstransmission success rate less than a threshold, such as 99.99%), a highreliability performance requirement (e.g., a communications transmissionsuccess rate greater than or equal to a threshold, such as 99.99%), ahigh data rate performance requirement (e.g., download and upload speedsabove a threshold, such as 50 Mbps), a low data rate performancerequirement (e.g., download and upload speeds less than or equal to athreshold, such as 50 Mbps), a high traffic density requirement (e.g.,greater than or equal to a threshold number of user devices pergeographical area, such as 10,000 user devices per square kilometer),and/or a low traffic density requirement (e.g., less than a thresholdnumber of user devices per geographical area, such as 10,000 userdevices per square kilometer).

The data network of example implementation(s) 100 can include varioustypes of data networks, such as the Internet, a third-party servicesnetwork, an operator services network, a private network, a wide areanetwork, and/or the like.

As shown in FIG. 1A, and by reference number 105, the UE can send a UEconfiguration request (e.g., a UE configuration message) to the basestation of the RAN to register the UE with the network and/or initiate acommunication session between the UE and the data network. As shown inFIG. 1A, the UE configuration request can include an S-NSSAI. TheS-NSSAI can be one of a plurality of S-NSSAI in an NSSAI of the UEconfiguration request. In some implementations, the UE configurationrequest can identify the data network (e.g., via a data networkidentifier) that is to be involved in a communication session with theUE. According to some implementations, to send the UE configurationrequest, the UE can run an application (e.g., a configurationapplication) that causes the UE to communicate with the AMF of the corenetwork, via the RAN, to request that an S-NSSAI associated with the UEbe associated with an NSI to permit the UE to engage in a communicationsession with the data network.

As shown in FIG. 1A, an S-NSSAI can include information elements thatpermit the core network (e.g., the NSSF) to select and/or associate theS-NSSAI with an NSI for the UE. Accordingly, the UE can utilize the NSI(as indicated by the NSSF and/or AMF, as described herein) for acommunication session associated with the S-NSSAI.

As shown in FIG. 1A, an S-NSSAI of the request can include aslice/service type (SST) field, a network slice type (NEST) field, aservice field, an entity/application selection field (a), anentity/application association field, and/or an inter-slice prioritylevel (ISPL) field. In some implementations, the NEST field, the servicefield, the entity/application selection field, the entity/applicationassociation field, and/or the ISPL field are included within a slicedifferentiator (SD) field of the S-NSSAI. According to someimplementations, the S-NSSAI can be configured such that fields of theS-NSSAI are maintained and/or identifiable by the UE, the RAN, the corenetwork, and/or the like. For example, the S-NSSAI can have a length of32 bits, with 8 bits being allocated for the SST and 24 bits beingallocated for the SD, and each information element of the SD can includea certain number of bits and/or be included within the SD in aparticular order or at particular locations of the S-NSSAI.

The SST field of the S-NSSAI can identify a service/slice type (e.g.,enhanced mobile broadband (eMBB) service, an ultra-reliable, low-latency(URLLC) service, a mobile Internet of Things (mIoT) service, and/or thelike) for a communication session involving the UE.

The NEST field of the S-NSSAI can include a NEST identifier thatidentifies a type of NSI that is capable of supporting one or moreapplications and/or services involved in a communication session thatuses the S-NSSAI to enable the UE to engage in the communicationsession. For example, the NEST can describe or identify a set ofcharacteristics that the NSI is to have to support a communicationsession associated with the S-NSSAI. In some implementations, suchcharacteristics can include a range of traffic QoS attributes (e.g.,latency greater than a threshold number of milliseconds), resourcesand/or NFs associated with the communication session, resource scalingpolicies, a set of corresponding network configurations, and/or thelike. In some implementations, the NEST field can include a NEST mappingfor a particular SST. In other words, each SST can have a unique mappingof NESTs. In some implementations, the NEST field can be allocated fourbits of the SD.

The service field can include a service identifier that identifies oneor more services that can be involved in the communication session. Forexample, such services can include enhanced mobile broadband (e.g., forproviding enhanced broadband access in dense areas, ultra-high bandwidthaccess in dense areas, broadband access in public transport systems,and/or the like), connected vehicles (e.g., for providingvehicle-to-everything (V2X) communications, such as vehicle-to-vehicle(V2V) communications, vehicle-to-infrastructure (V2I) communications,vehicle-to-network (V2N) communications, and vehicle-to-pedestrian (V2P)communications, and/or the like), real-time service (e.g., for providinginter-enterprise communications, intra-enterprise communications, mapsfor navigation, and/or the like), enhanced multi-media (e.g., forproviding broadcast services, on demand and live TV, mobile TV,augmented reality (AR), virtual reality (VR), internet protocol (IP)multi-media subsystem (IMS) service, and/or the like), internet ofthings (IoT) (e.g., for providing metering, lighting management inbuildings and cities, environmental monitoring, traffic control, and/orthe like), URLLC (e.g., for providing process automation, automatedfactories, tactile interaction, emergency communications, urgenthealthcare, and/or the like), mission critical push-to-talk (PTT), afixed wireless access category (e.g., for providing localized networkaccess and/or the like), and/or the like. In some implementations, twoor more service types can be mapped to a same NEST. For example, IMS andInternet can both be mapped to an eMBB NEST. In some implementations,the service field can be allocated seven bits of the SD.

The entity/application selection (a) field can include a selectionidentifier that identifies whether the entity/application associationfield identifies a customer or an application. For example, theselection identifier can be a Boolean logic value (e.g., “0” or “1,”“true” or “false,” etc.) or another value that differentiates whetherthe customer/application association field identifies a customer or anapplication. For example, a selection identifier value of “0” canindicate that the entity/application association field identifies anentity, and a selection identifier value of “1” can indicate that theentity/application association field identifies an application. In someimplementations, the entity/application selection field can be allocatedone bit of the SD.

The entity/application association field can include anentity/application identifier that identifies an entity or anapplication that is associated with the service provided in thecommunication session. For example, the entity can include one or moreapplication service providers capable of communicating with an end userassociated with the UE to provide the one or more services to the enduser via a communication session associated with the S-NSSAI. In someimplementations, the entity can be configured to monitor (e.g., via thecommunication session) the services at a slice level. Accordingly,different entities can be associated with different policies (e.g.,according to service level agreements (SLA) of the entities) that permitmonitoring of the services at the slice level. In some implementations,an entity can be associated with and/or allocated an isolated networkfor services and/or operations of the entity (e.g., according to an SLAof the entity). In this way, entity-specific information can be includedin an S-NSSAI to permit one or more policies associated with the entityto be followed for a communication session associated with the S-NSSAI.Accordingly, an entity can be assigned and/or be associated withspecific S-NSSAI that can be configured to be associated with specificNSIs, as described herein.

The application can include one or more applications of a UE (e.g., apublic safety application, a V2X application, an AR application, a VRapplication, a video-streaming application, etc.) that utilize a networkslice identified by an S-NSSAI. In some implementations, the applicationcan utilize multiple network slices to provide a particularfunctionality (e.g., a core functionality) of the application (referredto herein as a “multiple-slice application”). In some implementations, amultiple-slice application can be associated with a plurality ofcommunication sessions (e.g., respective communication sessions for themultiple network slices). For example, a V2X application can use acommunication session on an eMBB network slice for traffic relating toroad situation awareness data and a communication session on a URLLCnetwork slice for traffic relating to safety control data. In someimplementations, the entity/application association field can beallocated ten bits of the SD.

The ISPL field can include a priority identifier that identifies apriority level of an NSI that is to be selected for the S-NSSAI toensure that a priority, among network slices of the network, is given toa communication session associated with the S-NSSAI. As describedherein, traffic and services in one NSI should not impact traffic andservices of another NSI. However, if resources are limited, the ISPL canindicate which S-NSSAI are to be prioritized over other S-NSSAI. In thisway, a communication session, when carried via an NSI and associatedwith the S-NSSAI, can be given priority over other communicationsessions that are using other NSIs according to other S-NSSAI that didnot include such a priority (and vice versa). In some implementations, apriority of a group of associated S-NSSAI can be a highest priority(e.g., ISPL value) among the associated S-NSSAI. In someimplementations, the ISPL field can be allocated four bits of the SD.

Additionally, or alternatively, an ISPL can be allocated or assigned toS-NSSAI that do not include an SD. For example, an NSSF can use amapping of ISPLs for various SSTs of the S-NSSAI. In this way, the NSSFcan be configured to determine an inter-slice priority for S-NSSAIassociated with corresponding SSTs.

In this way, the UE can send a plurality of S-NSSAI (e.g., in a UEconfiguration request message) that include information elements thatpermit the RAN to determine whether the plurality of S-NSSAI areconfigured as a group of associated S-NSSAI.

As shown by reference number 110, the RAN can determine whether aplurality of S-NSSAI received from a UE (e.g., received in the UEconfiguration request) are configured as a group of associated S-NSSAI.In some implementations, the RAN can determine whether the plurality ofS-NSSAI are configured as a group in response to the UE configurationrequest. Additionally, or alternatively, the RAN can determine whetherthe plurality of S-NSSAI are configured as a group in response to atraffic flow of the UE. Additionally, or alternatively, the RAN candetermine whether the plurality of S-NSSAI are configured as a groupafter determining that the network has insufficient resources to supportone or more communication sessions of the network and/or one or moretraffic flows of the network.

In some implementations, the RAN can utilize information elements of theplurality of S-NSSAI to determine whether the plurality of S-NSSAI areconfigured as a group of associated S-NSSAI. For example, the RAN candetermine that the entity/application identifier (i.e., theentity/application identifier of the entity/application associationfield of the SD) of an S-NSSAI identifies an application based on theselection identifier (i.e., the selection identifier of theentity/application selection (a) field of the SD) of the S-NSSAI (e.g.,if the selection identifier has a value of “1” or “true” the RAN candetermine that the entity/application identifier identifies anapplication). Continuing with the previous example, the RAN can comparerespective entity/application identifiers (e.g., entity/applicationidentifiers that are determined to identify an application based on theselection identifier) of the plurality of S-NSSAI to determine a match,and determine that the plurality of S-NSSAI are a group of associatedS-NSSAI based on determining the match.

In some implementations, the RAN can determine whether the plurality ofS-NSSAI are configured as a group of associated S-NSSAI based on amapping of the S-NSSAI (e.g., a mapping configured in the RAN) to agroup of associated S-NSSAI. For example, respective identifiers of theS-NSSAI (e.g., S-NSSAI “11,” “23,” “50,” etc.) can be mapped to a groupidentifier (e.g., group “1,” “15,” etc.). In some implementations, anidentifier for an S-NSSAI can be a decimal representation, hexadecimalrepresentation, etc. of the S-NSSAI (i.e., a binary representation ofthe S-NSSAI). In some implementations, the mapping can be stored in adata structure (e.g., a data repository, a database, a table, a list,and/or the like) associated with the RAN (e.g., a CU-CP and/or a DU ofthe RAN). Additionally, or alternatively, the mapping can be stored in adata structure associated with the core network and provided to the RANvia messaging between the core network and the RAN, as described below.

In some implementations the group of associated S-NSSAI can include twoor more S-NSSAI. In some implementations, the group of associatedS-NSSAI can be associated with an application of a UE. For example, thegroup of associated S-NSSAI can provide a particular functionality to anapplication of a UE. In this way, the RAN can perform session admissionand/or preemption, scheduling, resource allocation, etc. so as not toimpair the particular functionality of the application (e.g., bydisrupting one or more communication sessions of the plurality ofS-NSSAI). In some implementations, the particular functionality can be acore functionality of the application (e.g., the application could notperform an intended function of the application without the corefunctionality). In some implementations, the particular functionalitycan be defined by an SLA associated with a multiple-slice application.

In some implementations, a CU (e.g., a CU-CP node) and/or a DU of a basestation of the RAN can determine whether a plurality S-NSSAI areconfigured as a group of associated S-NSSAI. For example, the mapping ofS-NSSAI to groups of associated S-NSSAI can be configured via amanagement plane of the RAN to thereby permit a CU and/or a DU of theRAN to determine whether a plurality S-NSSAI are configured as a groupof associated S-NSSAI.

Additionally, or alternatively, associations among S-NSSAI can beconfigured via a control plane of the RAN to permit a CU and/or a DU ofthe RAN to determine whether a plurality of S-NSSAI are configured as agroup of associated S-NSSAI. For example, after creating an initialcontext for a UE, the AMF of the core network can provide a CU-CP nodeof the RAN with information relating to the UE (e.g., a UE identifier)and information relating to one or more PDU sessions of the UE (e.g., aPDU session identifier, an S-NSSAI associated with the PDU session, aQoS flow-level parameter associated with the PDU session, etc.) via anN2 interface (e.g., via UE initial context setup request messages and/orPDU session resource setup request messages) to establish UE context atthe CU-CP node.

The CU-CP node can provide one or more CU-UP nodes of the RAN withinformation relating to the UE (e.g., a local UE identifier between theCU-CP node and the one or more CU-UP nodes), information relating to theone or more PDU sessions of the UE (e.g., a PDU session identifier, anS-NSSAI associated with the PDU session, a DRB associated with the PDUsession, etc.), and information relating to one or more DRBs associatedwith the PDU session (e.g., a DRB identifier, a QoS flow-level parameterassociated with the DRB, etc.) via the E1 interface (e.g., via bearercontext setup request messages) to establish UE context at the one ormore CU-UP nodes. In addition, the CU-CP node can provide one or moreDUs of the RAN with information relating to the UE (e.g., a local UEidentifier between the CU-CP node and the one or more DUs) andinformation relating to the one or more DRBs configured for the UE(e.g., a DRB identifier, an S-NSSAI associated with the DRB, a QoSflow-level parameter, etc.) via the F1-C interface (e.g., via UE contextsetup request messages) to establish UE context at the one or more DUs.In this way, a DRB can be associated with an S-NSSAI to permit a CU-CPnode and/or one or more DUs to determine associations among S-NSSAI andperform admission, preemption, scheduling, and/or resource allocationaccordingly, as described below.

As shown in FIG. 1B, and by reference number 115, the RAN can determine(e.g., based on determining that a plurality of S-NSSAI are configuredas a group of associated S-NSSAI) that a preference is to be given to amultiple-slice application relative to one or more applications that donot utilize multiple network slices (referred to herein as a“single-slice application”). In this way, the preference given to themultiple-slice application enables the RAN to avoid disruptions tocommunication sessions associated with the multiple-slice application.

The RAN can identify a single-slice application based on an S-NSSAIassociated with the single-slice application (e.g., an S-NSSAI providedby a UE requesting a connection to the network). For example, the RANcan identify the single-slice application by determining that theS-NSSAI is not associated with a group of associated S-NSSAI (e.g., anentity/application selection field of the S-NSSAI has a value of “0” or“false,” an entity/application association field of the S-NSSAI does notmatch an entity/application association field of another S-NSSAI, and/orthe S-NSSAI is not mapped to a group of associated S-NSSAI). In someimplementations, a multiple-slice application can be associated with afirst UE and a single-slice application can be associated with the firstUE or a second UE.

In some implementations, the RAN can determine that a preference is tobe given to one or more communication sessions associated with amultiple-slice application relative to a communication sessionassociated with a single-slice application. Additionally, oralternatively, the RAN can determine that a preference is to be given toone or more traffic flows associated with a multiple-slice applicationrelative to a traffic flow associated with a single-slice application.Additionally, or alternatively, the RAN can determine that a preferenceis to be given to one or more network slices associated with amultiple-slice application relative to a network slice associated with asingle-slice application. In some implementations, a CU (e.g., a CU-CPnode) and/or a DU of a base station of the RAN can determine that apreference is to be given to a multiple-slice application relative toone or more single-slice applications.

In some implementations, the RAN can determine a preference for a firstmultiple-slice application relative to a second multiple-sliceapplication. For example, when a resource contention exists between thefirst multiple-slice application and the second multiple-sliceapplication, the RAN can determine the preference for the firstmultiple-slice application if a priority associated with the firstmultiple-slice application is higher than a priority associated with thesecond multiple-slice application. In some implementations, a priorityassociated with a multiple-slice application is a highest priority(e.g., ISPL value) among a group of associated S-NSSAI associated withthe multiple-slice application. Additionally, or alternatively, apriority associated with a multiple-slice application can be configuredby a provider of the network (e.g., mapped to a group of associatedS-NSSAI associated with the multiple-slice application).

As shown by reference number 120, the RAN can perform one or moreactions (e.g., based on determining that the preference is to be givento a multiple-slice application). In some implementations, the RAN canperform the one or more actions in response to the UE configurationrequest. Additionally, or alternatively, the RAN can perform the one ormore actions in response to a traffic flow of the UE. Additionally, oralternatively, the RAN can perform the one or more actions afterdetermining that the network has insufficient resources to support oneor more communication sessions of the network and/or one or more trafficflows of the network.

In some implementations, an action performed by the RAN can relate toadmitting (e.g., admitting on a cellular layer of the network) one ormore communication sessions associated with a multiple-slice applicationand/or preempting one or more communication sessions associated with oneor more single-slice applications. For example, the RAN can determinethat insufficient network resources are available to support one or morecommunication sessions associated with a multiple-slice application andone or more communication sessions associated with one or moresingle-slice applications. Continuing with the previous example, basedon a preference given to the multiple slice-application, the RAN canadmit the one or more communication sessions associated with themultiple-slice application and not admit the one or more communicationsessions associated with the one or more single-slice applications(e.g., so as to admit all communication sessions associated with themultiple-slice application).

As another example, the RAN can determine that insufficient networkresources are available to support one or more communication sessionsassociated with a multiple-slice application. Continuing with theprevious example, based on a preference given to the multiple-sliceapplication, the RAN can preempt the one or more communication sessionsassociated with the one or more single-slice applications in order toadmit the one or more communication sessions associated with themultiple-slice application (e.g., so as to admit all communicationsessions associated with the multiple-slice application). In someimplementations, admitting the one or more communication sessionsassociated with the multiple-slice application can occur during ahandover of the one or more communication sessions from a first channelof the network (e.g., associated with a first base station) to a secondchannel of the network (e.g., associated with a second base station).

In some implementations, an action performed by the RAN can relate toscheduling traffic flows associated with a multiple-slice application(e.g., traffic flows of one or more communication sessions associatedwith the multiple-slice application). For example, the RAN can identifyone or more traffic flows associated with a multiple-slice applicationand one or more traffic flows associated with one or more single-sliceapplications. Continuing with the previous example, based on apreference given to the multiple-slice application, the RAN can schedulethe one or more traffic flows associated with the multiple-sliceapplication before the one or more traffic flows associated with the oneor more single-slice applications.

In some implementations, an action performed by the RAN can relate toallocating resources (e.g., DRBs) to one or more network slicesassociated with a multiple-slice application and/or reallocatingresources from one or more network slices associated with one or moresingle-slice applications to one or more network slices associated withthe multiple-slice application. For example, based on a preference givento a multiple-slice application, the RAN can allocate resources (e.g.,available resources) to one or more network slices associated with themultiple-slice application and not allocate the resources to one or morenetwork slices associated with one or more single-slice applications. Asanother example, the RAN can determine that one or more network slicesassociated with a multiple-slice application have insufficientresources. Continuing with the previous example, based on a preferencegiven to the multiple-slice application, the RAN can reallocateresources from one or more network slices associated with one or moresingle-slice applications to the one or more network slices associatedwith the multiple-slice application.

In this way, the one or more actions enable the RAN to deliver amultiple-slice application to a UE without disruption to one or morecommunication sessions and/or one or more network slices utilized by themultiple-slice application. Accordingly, impairment to multiple-sliceapplications (e.g., impairment caused by admission and/or preemption,scheduling, and/or resource allocation performed by the RAN withoutregard to associated network slices) can be reduced, thus providing fora more efficient use of network resources.

In some implementations, the one or more actions can be performed basedon a preference given to a first multiple-slice application relative toa second multiple-slice application, as described above.

In some implementations, a CU (e.g., a CU-CP node) and/or a DU of a basestation of the RAN can perform the one or more actions. For example, aCU-CP node of the RAN can perform the one or more actions using an RRCfunction and/or a PDCP function hosted by the CU-CP node. As anotherexample, one or more DUs of the RAN can perform the one or more actionsusing an RLC function and/or a MAC scheduler function hosted by the oneor more DUs.

As indicated above, FIGS. 1A and 1B are provided as examples. Otherexamples can differ from what is described with regard to FIGS. 1A and1B.

FIG. 2 is a diagram of an example implementation 200 described herein.As shown in FIG. 2, example implementation 200 can include a networkdata analytics function (NWDAF) and/or a self-organizing network (SON)function. The SON function and/or NWDAF can provide lifecyclemanagement, placement, and/or configuration of network resources; canscale up or down network resources; can provide coverage and capacityoptimization for the network; can provide mobility robustness for thenetwork; can provide anomaly detection, diagnosis, and/or healing forthe network; can provide automatic neighbor relation setup for thenetwork; can provide resource identifier allocation for the network;and/or the like.

In some implementations, the SON function and/or the NWDAF can beassociated with a core network of a network, an edge domain of thenetwork, and/or a RAN of the network (e.g., a base station of the RAN).In some implementations, the SON function and the NWDAF can address twodifferent roles in the network. For example, the SON function can handlenetwork level configuration aspects. The NWDAF can handle control planeaspects associated with UEs (e.g., per session resource tuning). TheNWDAF can trigger network function placement options through othernetwork functions, such as a NSSF, a PCF, and/or the like.

In some implementations, the SON function and/or the NWDAF can include adata collection component 205. Data collection component 205 can obtaindata from one or more components of the network (e.g., in real time,near-real time, periodically, and/or the like). For example, datacollection component 205 can obtain core data that can includesubscriber data and profiles stored by a UDM of the core network; datautilized by a UDM of the core network for fixed access, mobile access,and/or the like, in the network; data utilized by an AUSF of the corenetwork to provide authentication services and to support authenticationof UEs associated with the network; data utilized by an NSSF of the corenetwork to select network slices and to customize each network slice fordifferent services; data utilized by a PCF of the core network toprovide a policy framework that incorporates network slicing, roaming,packet processing, mobility management, and/or the like; data utilizedby an NEF of the core network to support a service discovery function ofthe network; data utilized by an AMF of the core network to enable theAMF to act as a termination point for non-access stratum (NAS)signaling, mobility management, etc.; and/or the like.

As another example, data collection component 205 can obtain edge datathat can include data utilized by a PCF of the edge domain to provide apolicy framework that incorporates network slicing, roaming, packetprocessing, mobility management, and/or the like; data utilized by anSMF of the edge domain to support the establishment, modification, andrelease of communications sessions in the network; data utilized by auser plane function (UPF) of the edge domain to enable the UPF to serveas an anchor point for intraRAT and/or interRAT mobility; data utilizedby a UPF of the edge domain to apply rules to packets, such as rulespertaining to packet routing, traffic reporting, handling user planequality of service, etc.; and/or the like.

As a further example, data collection component 205 can obtain RAN datathat can include data utilized by a base station of the RAN to provideone or more cells that cover geographic areas; data utilized by a basestation of the RAN to perform scheduling and/or resource management forUEs covered by the base station; data indicating subscriber usagepatterns in the RAN; data indicating mobility patterns in the RAN at anetwork slice level and/or a RAN level; data indicating temporal and/orgeographic traffic patterns (e.g., at a network slice level and at a RANlevel); data indicating user device mix, characteristics, etc.; and/orthe like.

In some implementations, data collection component 205 can include SLAdata 210. SLA data 210 can include data relating to one or more SLAsbetween a provider of the network and one or more entities using thenetwork. An SLA can define a level of service to be provided to anentity with regard to uplink transmission speed, downlink transmissionspeed, uplink bandwidth, downlink bandwidth, network uptime, and/or thelike. In some implementations, an SLA can relate to a network slice, aservice, an application, and/or the like.

In some implementations, data collection component 205 can include ananalytics module 215. Analytics module 215 can provide analytics data(e.g., in real time, near-real time, periodically, and/or the like). Insome implementations, the analytics data can include data identifyingtrends and/or patterns associated with the network; data indicating bitrates through network resources; data indicating collision and packetdrop rates associated with the network; data indicating latenciesassociated with the network; data indicating packets affected bysecurity policies; flow data associated with the network; security dataassociated with the network; interpreted packet flows from the network;log data from the network; time-series monitoring data associated withthe network; synthetic network data; and/or the like.

In some implementations, the SON function and/or the NWDAF can includeS-NSSAI mapping component 220. For example, S-NSSAI mapping component220 can contain S-NSSAI mapping data relating to groups of associatedS-NSSAI, as described above.

In some implementations, the SON function and/or the NWDAF can includeS-NSSAI association analytics component 225. For example, S-NSSAIassociation analytics component 225 can provide S-NSSAI analytics data(e.g., in real time, near-real time, periodically, and/or the like). Insome implementations, the S-NSSAI analytics data can include dataidentifying trends and/or patterns associated with groups of associatedS-NSSAI; data indicating bit rates through network resources associatedwith groups of associated S-NSSAI; data indicating latencies associatedwith groups of associated S-NSSAI; flow data associated with groups ofassociated S-NSSAI; and/or the like.

In some implementations, data collection component 205 can include anartificial intelligence (AI) module 230. AI module 230 can process(e.g., using a machine learning model) core data, edge data, RAN data,analytics data, SLA data, S-NSSAI mapping data, and/or S-NSSAI analyticsdata to determine one or more actions to perform with regard to the corenetwork, the edge domain, and/or the RAN. For example, AI module 230 candetermine to generate an SLA for an application (e.g., when no SLA forthe application exists) that is based on one or more SLAs for one ormore network slices associated with the application, one or moreservices associated with the application, and/or the like. As anotherexample, AI module 230 can determine to tune network slice policiesand/or configurations (e.g., network slice policies and/orconfigurations at the network core and/or the RAN) so as to meet or toexceed an SLA for an application and/or an SLA generated for anapplication.

As indicated above, FIG. 2 is provided as an example. Other examples candiffer from what is described with regard to FIG. 2.

FIG. 3 is a diagram of an example environment 300 in which systemsand/or methods, described herein, can be implemented. As shown in FIG.3, environment 300 can include a UE 310, a RAN 320, a base station 322,a core network 330, and a data network 340. Devices of environment 300can interconnect via wired connections, wireless connections, or acombination of wired and wireless connections.

UE 310 includes one or more devices capable of communicating with RAN320 and/or a data network 340 (e.g., via core network 330). For example,UE 310 can include a wireless communication device, a radiotelephone, apersonal communications system (PCS) terminal (e.g., that can combine acellular radiotelephone with data processing and data communicationscapabilities), a smart phone, a laptop computer, a tablet computer, apersonal gaming system, user equipment, and/or a similar device. UE 310can be capable of communicating using uplink (e.g., UE to RAN)communications, downlink (e.g., RAN to UE) communications, and/orsidelink (e.g., UE-to-UE) communications. In some implementations, UE310 can include a machine-type communication (MTC) UE, such as anevolved or enhanced MTC (eMTC) UE. In some implementations, UE 310 caninclude an Internet of things (IoT) UE, such as a narrowband IoT(NB-IoT) UE and/or the like.

RAN 320 includes one or more devices capable of communicating with UE310 using a cellular RAT. For example, RAN 320 can include a basestation 322, a base transceiver station, a radio base station, a node B,an evolved node B (eNB), a gNB, a base station subsystem, a cellularsite, a cellular tower (e.g., a cell phone tower, a mobile phone tower,and/or the like), an access point, a transmit receive point (TRP), aradio access node, a macrocell base station, a microcell base station, apicocell base station, a femtocell base station, or a similar type ofdevice. In some implementations, base station 322 has the samecharacteristics and functionality of RAN 320, and vice versa. RAN 320can transfer traffic between UE 310 (e.g., using a cellular RAT), one ormore other RANs 320 (e.g., using a wireless interface or a backhaulinterface, such as a wired backhaul interface), and/or core network 330.RAN 320 can provide one or more cells that cover geographic areas. SomeRANs 320 can be mobile base stations. Some RANs 320 can be capable ofcommunicating using multiple RATs.

In some implementations, RAN 320 can perform scheduling and/or resourcemanagement for UEs 310 covered by RAN 320 (e.g., UEs 310 covered by acell provided by RAN 320). In some implementations, RAN 320 can becontrolled or coordinated by a network controller, which can performload balancing, network-level configuration, and/or the like. Thenetwork controller can communicate with RAN 320 via a wireless orwireline backhaul. In some implementations, RAN 320 can include anetwork controller, a SON module or component, or a similar module orcomponent. In other words, RAN 320 can perform network control,scheduling, and/or network management functions (e.g., for other RAN 320and/or for uplink, downlink, and/or sidelink communications of UEs 310covered by RAN 320). In some implementations, RAN 320 can apply networkslice policies to perform the network control, scheduling, and/ornetwork management functions. In some implementations, RAN 320 caninclude a central unit and multiple distributed units. The central unitcan coordinate access control and communication with regard to themultiple distributed units. The multiple distributed units can provideUEs 310 and/or other RANs 320 with access to data network 340 via corenetwork 330.

Core network 330 includes various types of core network architectures,such as a 5G Next Generation (NG) Core (e.g., core network 400 of FIG.4), a Long-Term Evolution (LTE) Evolved Packet Core (EPC), and/or thelike. In some implementations, core network 330 can be implemented onphysical devices, such as a gateway, a mobility management entity,and/or the like. In some implementations, the hardware and/or softwareimplementing core network 330 can be virtualized (e.g., through the useof network function virtualization and/or software-defined networking),thereby allowing for the use of composable infrastructure whenimplementing core network 330. In this way, networking, storage, andcompute resources can be allocated to implement the functions of corenetwork 330 (described with regard to FIG. 4) in a flexible manner asopposed to relying on dedicated hardware and software to implement thesefunctions.

Data network 340 includes one or more wired and/or wireless datanetworks. For example, data network 340 can include an IP MultimediaSubsystem (IMS), a public land mobile network (PLMN), a local areanetwork (LAN), a wide area network (WAN), a metropolitan area network(MAN), a private network such as a corporate intranet, an ad hocnetwork, the Internet, a fiber optic-based network, a cloud computingnetwork, a third party services network, an operator services network,and/or the like, and/or a combination of these or other types ofnetworks.

The number and arrangement of devices and networks shown in FIG. 3 areprovided as an example. In practice, there can be additional devicesand/or networks, fewer devices and/or networks, different devices and/ornetworks, or differently arranged devices and/or networks than thoseshown in FIG. 3. Furthermore, two or more devices shown in FIG. 3 can beimplemented within a single device, or a single device shown in FIG. 3can be implemented as multiple, distributed devices. Additionally, oralternatively, a set of devices (e.g., one or more devices) ofenvironment 300 can perform one or more functions described as beingperformed by another set of devices of environment 300.

FIG. 4 is a diagram of an example functional architecture of a corenetwork 400 in which systems and/or methods, described herein, can beimplemented. For example, FIG. 4 can show an example functionalarchitecture of a 5G core network included in a 5G wirelesstelecommunications system. In some implementations, the examplefunctional architecture can be implemented by a core network (e.g., corenetwork 330 of FIG. 3) and/or one or more of devices (e.g., a devicedescribed with respect to FIG. 5). While the example functionalarchitecture of core network 400 shown in FIG. 4 can be an example of aservice-based architecture, in some implementations, core network 400can be implemented as a reference-point architecture.

As shown in FIG. 4, core network 400 can include a number of functionalelements. The functional elements can include, for example, a NetworkData Analytics Function (NWDAF) 402, a Network Slice Selection Function(NSSF) 404, a Network Exposure Function (NEF) 406, an AuthenticationServer Function (AUSF) 408, a Unified Data Management (UDM) component410, a Policy Control Function (PCF) 412, an Application Function (AF)414, an Access and Mobility Management Function (AMF) 416, a SessionManagement Function (SMF) 418, and a User Plane Function (UPF) 420.These functional elements can be communicatively connected via a messagebus 422, which can be comprised of one or more physical communicationchannels and/or one or more virtual communication channels. Each of thefunctional elements shown in FIG. 4 is implemented on one or moredevices associated with a wireless telecommunications system. In someimplementations, one or more of the functional elements can beimplemented on physical devices, such as an access point, a basestation, a gateway, a server, and/or the like. In some implementations,one or more of the functional elements can be implemented on one or morecomputing devices of a cloud computing environment associated with thewireless telecommunications system. In some implementations, the corenetwork 400 can be operatively connected to a RAN 424, a data network426, and/or the like, via wired and/or wireless connections with UPF420.

NWDAF 402 can provide network analysis information upon request fromnetwork functions. For example, a network function can request, fromNWDAF 402, specific analysis information on a load level associated witha network slice. Alternatively, the network function can use a subscribeservice to ensure that the network function is notified by NWDAF 402 ifthe load level of a network slice changes or reaches a specificthreshold.

NSSF 404 can select network slice instances for UEs, where NSSF 404 candetermine a set of network slice policies to be applied at the RAN 424.By providing network slicing, NSSF 404 allows an operator to deploymultiple substantially independent end-to-end networks potentially withthe same infrastructure. In some implementations, each slice can becustomized for different services. NEF 406 can support the exposure ofcapabilities and/or events in the wireless telecommunications system tohelp other entities in the wireless telecommunications system discovernetwork services and/or utilize network resources efficiently.

AUSF 408 can act as an authentication server and support the process ofauthenticating UEs in the wireless telecommunications system. UDM 410can store subscriber data and profiles in the wirelesstelecommunications system. UDM 410 can be used for fixed access, mobileaccess, and/or the like, in core network 400. PCF 412 can provide apolicy framework that incorporates network slicing, roaming, packetprocessing, mobility management, and/or the like.

AF 414 can determine whether UEs provide preferences for a set ofnetwork slice policies and support application influence on trafficrouting, access to NEF 406, policy control, and/or the like. AMF 416 canprovide authentication and authorization of UEs. SMF 418 can support theestablishment, modification, and release of communications sessions inthe wireless telecommunications system. For example, SMF 418 canconfigure traffic steering policies at UPF 420, enforce UE IP addressallocation and policies, and/or the like. AMF 416 and SMF 418 can act asa termination point for Non-Access Stratum (NAS) signaling, mobilitymanagement, and/or the like. SMF 418 can act as a termination point forsession management related to NAS. RAN 424 can send information (e.g.the information that identifies the UE) to AMF 416 and/or SMF 418 viaPCF 412.

UPF 420 can serve as an anchor point for intra/inter RAT mobility. UPF420 can apply rules to packets, such as rules pertaining to packetrouting, traffic reporting, handling user plane Quality of Service(QoS), and/or the like. UPF 420 can determine an attribute ofapplication-specific data that is communicated in a communicationssession. UPF 420 can receive information (e.g., the information thatidentifies the communications attribute of the application) from RAN 424via SMF 418 or an Application Programming Interface (API). Message bus422 represents a communication structure for communication among thefunctional elements. In other words, message bus 422 can permitcommunication between two or more functional elements. Message bus 422can be a message bus, HTTP/2 proxy server, and/or the like.

RAN 424 can include a base station and be operatively connected, via awired and/or wireless connection, to the core network 400 through UPF420. RAN 424 can facilitate communications sessions between UEs and datanetwork 426 by communicating application-specific data between RAN 424and core network 400. Data network 426 can include various types of datanetworks, such as the Internet, a third-party services network, anoperator services network, a private network, a wide area network,and/or the like.

The number and arrangement of functional elements shown in FIG. 4 areprovided as an example. In practice, there can be additional functionalelements, fewer functional elements, different functional elements, ordifferently arranged functional elements than those shown in FIG. 4.Furthermore, two or more functional elements shown in FIG. 4 can beimplemented within a single device, or a single functional element shownin FIG. 4 can be implemented as multiple, distributed devices.Additionally, or alternatively, a set of functional elements (e.g., oneor more functional elements) of core network 400 can perform one or morefunctions described as being performed by another set of functionalelements of core network 400.

FIG. 5 is a diagram of example components of a device 500. Device 500can correspond to, or can implement, UE 310, a base station (e.g., basestation 322) of RAN 320, one or more functional elements or devices ofcore network 330, one or more functional elements of core network 400,and/or a device of data network 340. In some implementations, UE 310, abase station (e.g., base station 322) of RAN 320, one or more functionalelements or devices of core network 330, one or more functional elementsof core network 400, and/or a device of data network 340 can include oneor more devices 500 and/or one or more components of device 500. Asshown in FIG. 5, device 500 can include a bus 510, a processor 520, amemory 530, a storage component 540, an input component 550, an outputcomponent 560, and a communication interface 570.

Bus 510 includes a component that permits communication among thecomponents of device 500. Processor 520 is implemented in hardware,firmware, or a combination of hardware and software. Processor 520 is acentral processing unit (CPU), a graphics processing unit (GPU), anaccelerated processing unit (APU), a microprocessor, a microcontroller,a digital signal processor (DSP), a field-programmable gate array(FPGA), an application-specific integrated circuit (ASIC), or anothertype of processing component. In some implementations, processor 520includes one or more processors capable of being programmed to perform afunction. Memory 530 includes a random access memory (RAM), a read onlymemory (ROM), and/or another type of dynamic or static storage device(e.g., a flash memory, a magnetic memory, and/or an optical memory) thatstores information and/or instructions for use by processor 520.

Storage component 540 stores information and/or software related to theoperation and use of device 500. For example, storage component 540 caninclude a hard disk (e.g., a magnetic disk, an optical disk, amagneto-optic disk, and/or a solid state disk), a compact disc (CD), adigital versatile disc (DVD), a floppy disk, a cartridge, a magnetictape, and/or another type of non-transitory computer-readable medium,along with a corresponding drive.

Input component 550 includes a component that permits device 500 toreceive information, such as via user input (e.g., a touch screendisplay, a keyboard, a keypad, a mouse, a button, a switch, and/or amicrophone). Additionally, or alternatively, input component 550 caninclude a sensor for sensing information (e.g., a global positioningsystem (GPS) component, an accelerometer, a gyroscope, and/or anactuator). Output component 560 includes a component that providesoutput information from device 500 (e.g., a display, a speaker, and/orone or more light-emitting diodes (LEDs)).

Communication interface 570 includes a transceiver-like component (e.g.,a transceiver and/or a separate receiver and transmitter) that enablesdevice 500 to communicate with other devices, such as via a wiredconnection, a wireless connection, or a combination of wired andwireless connections. Communication interface 570 can permit device 500to receive information from another device and/or provide information toanother device. For example, communication interface 570 can include anEthernet interface, an optical interface, a coaxial interface, aninfrared interface, a radio frequency (RF) interface, a universal serialbus (USB) interface, a wireless local area network interface, a cellularnetwork interface, or the like.

Device 500 can perform one or more processes described herein. Device500 can perform these processes based on processor 520 executingsoftware instructions stored by a non-transitory computer-readablemedium, such as memory 530 and/or storage component 540. Acomputer-readable medium is defined herein as a non-transitory memorydevice. A memory device includes memory space within a single physicalstorage device or memory space spread across multiple physical storagedevices.

Software instructions can be read into memory 530 and/or storagecomponent 540 from another computer-readable medium or from anotherdevice via communication interface 570. When executed, softwareinstructions stored in memory 530 and/or storage component 540 can causeprocessor 520 to perform one or more processes described herein.Additionally, or alternatively, hardwired circuitry can be used in placeof or in combination with software instructions to perform one or moreprocesses described herein. Thus, implementations described herein arenot limited to any specific combination of hardware circuitry andsoftware.

The number and arrangement of components shown in FIG. 5 are provided asan example. In practice, device 500 can include additional components,fewer components, different components, or differently arrangedcomponents than those shown in FIG. 5. Additionally, or alternatively, aset of components (e.g., one or more components) of device 500 canperform one or more functions described as being performed by anotherset of components of device 500.

FIG. 6 is a flow chart of an example process 600 for multiple-sliceapplication delivery based on network slice associations. In someimplementations, one or more process blocks of FIG. 6 can be performedby a base station of a RAN (e.g., base station 322 of RAN 320). In someimplementations, one or more process blocks of FIG. 6 can be performedby another device or a group of devices separate from or including thebase station of the RAN, such as a UE (e.g., UE 310), a core network(e.g., core network 330), and/or the like.

As shown in FIG. 6, process 600 can include receiving information thatrelates to a first application of first user equipment, wherein theinformation includes a plurality of S-NSSAI, and wherein the pluralityof S-NSSAI identify a plurality of network slices (block 610). Forexample, the base station of the RAN (e.g., using processor 520, memory530, storage component 540, input component 550, communication interface570, and/or the like) can receive information that relates to a firstapplication of first user equipment, as described above. In someimplementations, the information includes a plurality of S-NSSAI. Insome implementations, the plurality of S-NSSAI identify a plurality ofnetwork slices.

As further shown in FIG. 6, process 600 can include determining whetherthe plurality of S-NSSAI are configured as a group of associatedS-NSSAI, wherein a configuration of the plurality of S-NSSAI as thegroup of associated S-NSSAI indicates that the first applicationutilizes the plurality of network slices to provide a particularfunctionality of the first application (block 620). For example, thebase station of the RAN (e.g., using processor 520, memory 530, storagecomponent 540, and/or the like) can determine whether the plurality ofS-NSSAI are configured as a group of associated S-NSSAI, as describedabove. In some implementations, a configuration of the plurality ofS-NSSAI as the group of associated S-NSSAI indicates that the firstapplication utilizes the plurality of network slices to provide aparticular functionality of the first application.

As further shown in FIG. 6, process 600 can include determining that apreference is to be given to one of: one or more communication sessionsassociated with the first application relative to a communicationsession associated with a second application, that does not utilizemultiple network slices, of the first user equipment or second userequipment; one or more traffic flows associated with the firstapplication relative to a traffic flow associated with the secondapplication; or the plurality of network slices relative to a networkslice associated with the second application (block 630). For example,the base station of the RAN (e.g., using processor 520, memory 530,storage component 540, and/or the like) can determine that a preferenceis to be given to one of: one or more communication sessions associatedwith the first application relative to a communication sessionassociated with a second application, that does not utilize multiplenetwork slices, of the first user equipment or second user equipment;one or more traffic flows associated with the first application relativeto a traffic flow associated with the second application; or theplurality of network slices relative to a network slice associated withthe second application, as described above.

As further shown in FIG. 6, process 600 can include performing one ormore actions based on determining the preference to thereby facilitatethe particular functionality of the first application (block 640). Forexample, the base station of the RAN (e.g., using processor 520, memory530, storage component 540, input component 550, output component 560,communication interface 570, and/or the like) can perform one or moreactions based on determining the preference to thereby facilitate theparticular functionality of the first application, as described above.

Process 600 can include additional implementations, such as any singleimplementation or any combination of implementations described belowand/or in connection with one or more other processes describedelsewhere herein.

In some implementations, the one or more actions can include one or moreof: admitting the one or more communication sessions associated with thefirst application and not admitting the communication session associatedwith the second application; preempting the communication sessionassociated with the second application for the one or more communicationsessions associated with the first application; scheduling the one ormore traffic flows associated with the first application before thetraffic flow associated with the second application; allocatingresources to one or more of the plurality of network slices and notallocating the resources to the network slice associated with the secondapplication; or reallocating resources from the network slice associatedwith the second application to one or more of the plurality of networkslices. In some implementations, admitting the one or more communicationsessions associated with the first application is to occur during ahandover of the one or more communication sessions from a first channelto a second channel of a network associated with the plurality ofS-NSSAI.

In some implementations, determining whether the plurality of S-NSSAIare configured as the group of associated S-NSSAI can includedetermining whether a first slice differentiator (SD) field of a firstS-NSSAI of the plurality of S-NSSAI and a second SD field of a secondS-NSSAI of the plurality of S-NSSAI contain an identifier of the firstapplication. In some implementations, determining whether the pluralityof S-NSSAI are configured as the group of associated S-NSSAI can includedetermining whether the plurality of S-NSSAI are configured as the groupof associated S-NSSAI based on a mapping of the plurality of S-NSSAI tothe group of associated S-NSSAI.

In some implementations, the particular functionality of the firstapplication is defined by a service level agreement. In someimplementations, the information is received in a request to registerthe first user equipment with a network associated with the plurality ofS-NSSAI, or a request to initiate one or more protocol data unitsessions.

Although FIG. 6 shows example blocks of process 600, in someimplementations, process 600 can include additional blocks, fewerblocks, different blocks, or differently arranged blocks than thosedepicted in FIG. 6. Additionally, or alternatively, two or more of theblocks of process 600 can be performed in parallel.

The foregoing disclosure provides illustration and description, but isnot intended to be exhaustive or to limit the implementations to theprecise form disclosed. Modifications and variations can be made inlight of the above disclosure or can be acquired from practice of theimplementations.

As used herein, the term “component” is intended to be broadly construedas hardware, firmware, or a combination of hardware and software.

Some implementations are described herein in connection with thresholds.As used herein, satisfying a threshold can, depending on the context,refer to a value being greater than the threshold, more than thethreshold, higher than the threshold, greater than or equal to thethreshold, less than the threshold, fewer than the threshold, lower thanthe threshold, less than or equal to the threshold, equal to thethreshold, etc., depending on the context.

To the extent the aforementioned implementations collect, store, oremploy personal information of individuals, it should be understood thatsuch information shall be used in accordance with all applicable lawsconcerning protection of personal information. Additionally, thecollection, storage, and use of such information can be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as can be appropriate for thesituation and type of information. Storage and use of personalinformation can be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

It will be apparent that systems and/or methods described herein can beimplemented in different forms of hardware, firmware, and/or acombination of hardware and software. The actual specialized controlhardware or software code used to implement these systems and/or methodsis not limiting of the implementations. Thus, the operation and behaviorof the systems and/or methods are described herein without reference tospecific software code—it being understood that software and hardwarecan be used to implement the systems and/or methods based on thedescription herein.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various implementations. In fact,many of these features can be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below can directly depend on only one claim, thedisclosure of various implementations includes each dependent claim incombination with every other claim in the claim set.

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems, and can be used interchangeably with “one or more.” Furthermore,as used herein, the term “set” is intended to include one or more items(e.g., related items, unrelated items, a combination of related andunrelated items, etc.), and can be used interchangeably with “one ormore.” Where only one item is intended, the phrase “only one” or similarlanguage is used. Also, as used herein, the terms “has,” “have,”“having,” or the like are intended to be open-ended terms. Further, thephrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A method, comprising: receiving, by a device,information that relates to a first application of a first userequipment, wherein the information includes a plurality ofsingle-network slice selection assistance information (S-NSSAI),determining, by the device and based on the plurality of S-NSSAI beingconfigured as a group of associated S-NSSAI, a preference for the firstapplication, relative to a second application that does not utilizemultiple network slices, when the first application is associated withthe group of associated S-NSSAI, wherein a configuration of theplurality of S-NSSAI as the group of associated S-NSSAI indicates thatthe first application utilizes a plurality of network slices to providea particular functionality of the first application; and performing, bythe device, one or more actions based on determining the preference tothereby facilitate the particular functionality of the firstapplication.
 2. The method of claim 1, further comprising: determiningwhether the plurality of S-NSSAI are configured as the group ofassociated S-NSSAI based on one or more of: whether a network associatedwith the plurality of S-NSSAI has insufficient resources to support oneor more communication sessions, an entity identifier of the plurality ofS-NSSAI, or a mapping of the plurality of S-NSSAI to the group ofassociated S-NSSAI.
 3. The method of claim 1, wherein the one or moreactions include one or more of: admitting one or more communicationsessions associated with the first application and not admitting acommunication session associated with the second application, preemptingthe communication session associated with the second application for theone or more communication sessions associated with the firstapplication, scheduling one or more traffic flows associated with thefirst application before traffic flow associated with the secondapplication, allocating resources to one or more of the plurality ofnetwork slices and not allocating the resources to a network sliceassociated with the second application, or reallocating resources from anetwork slice associated with the second application to one or more ofthe plurality of network slices.
 4. The method of claim 1, furthercomprising: determining, by the device, whether the plurality of S-NSSAIare configured as the group of associated S-NSSAI based on aninter-slice priority level (ISPL) field.
 5. The method of claim 1,further comprising: determining whether a first slice differentiator(SD) field of a first S-NSSAI of the plurality of S-NSSAI and a secondSD field of a second S-NSSAI of the plurality of S-NSSAI contain anidentifier of the first application.
 6. The method of claim 1, whereinthe particular functionality of the first application is a corefunctionality.
 7. The method of claim 1, further comprising: determiningwhether the plurality of S-NSSAI are configured as the group ofassociated S-NSSAI based on one or more traffic flows of a networkassociated with the plurality of S-NSSAI.
 8. A device, comprising: oneor more memories; and one or more processors, communicatively coupled tothe one or more memories, to: receive information that relates to afirst application of a first user equipment, wherein the informationincludes a plurality of single-network slice selection assistanceinformation (S-NSSAI), wherein the plurality of S-NSSAI identify aplurality of network slices; determine, based on the plurality ofS-NSSAI being configured as a group of associated S-NSSAI, a preferencefor the first application, relative to a second application that doesnot utilize multiple network slices, when the first application isassociated with the group of associated S-NSSAI, wherein a configurationof the plurality of S-NSSAI as the group of associated S-NSSAI indicatesthat the first application utilizes the plurality of network slices toprovide a particular functionality of the first application; and performone or more actions based on determining the preference to therebyfacilitate the particular functionality of the first application.
 9. Thedevice of claim 8, wherein the one or more processors, when performingthe one or more actions, are to one or more of: preempt a communicationsession associated with the second application for one or morecommunication sessions associated with the first application, scheduleone or more traffic flows associated with the first application beforetraffic flow associated with the second application, allocate resourcesto one or more of the plurality of network slices and not allocate theresources to a network slice associated with the second application, orreallocate resources from a network slice associated with the secondapplication to one or more of the plurality of network slices.
 10. Thedevice of claim 8, wherein the one or more processors, when performingthe one or more actions, are to: admit one or more communicationsessions associated with the first application and not admit acommunication session associated with the second application, whereinadmitting the one or more communication sessions associated with thefirst application is to occur during a handover of the one or morecommunication sessions from a first channel to a second channel of anetwork associated with the plurality of S-NSSAI.
 11. The device ofclaim 8, wherein the one or more processors are further to: determinewhether the plurality of S-NSSAI are configured as the group ofassociated S-NSSAI based on a mapping of the plurality of S-NSSAI to thegroup of associated S-NSSAI.
 12. The device of claim 8, wherein the oneor more processors are further to: determine whether the plurality ofS-NSSAI are configured as the group of associated S-NSSAI based on oneor more traffic flows of a network associated with the plurality ofS-NSSAI.
 13. The device of claim 8, wherein the one or more processorsare further to: determine whether the plurality of S-NSSAI areconfigured as the group of associated S-NSSAI based on an inter-slicepriority level (ISPL) field.
 14. The device of claim 8, wherein theinformation is received in a request to register the first userequipment with a network associated with the plurality of S-NSSAI.
 15. Anon-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions that, when executed byone or more processors, cause the one or more processors to: receiveinformation that relates to a first application of a first userequipment, wherein the information includes a plurality ofsingle-network slice selection assistance information (S-NSSAI), whereinthe plurality of S-NSSAI identify a plurality of network slices;determine, based on the plurality of S-NSSAI being configured as a groupof associated S-NSSAI, a preference for the first application, relativeto a second application that does not utilize multiple network slices,when the first application is associated with the group of associatedS-NSSAI, wherein a configuration of the plurality of S-NSSAI as thegroup of associated S-NSSAI indicates that the first applicationutilizes the plurality of network slices to provide a particularfunctionality of the first application; and perform one or more actionsbased on determining the preference to thereby facilitate the particularfunctionality of the first application.
 16. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, that cause the one or more processors to perform the oneor more actions, cause the one or more processors to one or more of:admit one or more communication sessions associated with the firstapplication and not admit a communication session associated with thesecond application, preempt a communication session associated with thesecond application for one or more communication sessions associatedwith the first application, schedule one or more traffic flowsassociated with the first application before traffic flow associatedwith the second application, allocate resources to one or more of theplurality of network slices and not allocate the resources to a networkslice associated with the second application, or reallocate resourcesfrom a network slice associated with the second application to one ormore of the plurality of network slices.
 17. The non-transitorycomputer-readable medium of claim 15, wherein the particularfunctionality of the first application is a core functionality.
 18. Thenon-transitory computer-readable medium of claim 15, wherein the one ormore instructions, that further cause the one or more processors to:determine whether the plurality of S-NSSAI are configured as the groupof associated S-NSSAI based on one or more traffic flows of a networkassociated with the plurality of S-NSSAI.
 19. The non-transitorycomputer-readable medium of claim 15, wherein the one or moreinstructions, that further cause the one or more processors to:determine whether the plurality of S-NSSAI are configured as the groupof associated S-NSSAI based on a mapping of the plurality of S-NSSAI tothe group of associated S-NSSAI, wherein the mapping is configured in aradio access network that is associated with the first user equipmentand a second user equipment.
 20. The non-transitory computer-readablemedium of claim 15, wherein the particular functionality of the firstapplication is defined by a service level agreement.